Hi,
I am creating a linkset between two modules using dxl... I see the linkset in the link module. But when I go and opened the source module properties -> Linkset -> "I dont see the linkset which i created". We enabled link paring restriction "Only allow outgoing links as specified in the above list" Can some one help me how to add this linkset to the source module.... Please find the code below. Thanks!
Here is my code:
Module linkModule = read("/" projectName "/Reqmts Links", true)
string optionModName = "/" projectName "/03. Functional Options" "/"moduleName
string custModName = "/" projectName "/02. Orders" "/"customerName "/"configName " " exportDate
Linkset lset = create(linkModule, optionModName , custModName)
SystemAdmin - Fri Sep 11 09:49:37 EDT 2009 |
|
Re: Linkset not appearing in the Module mcnairk - Fri Sep 11 10:15:40 EDT 2009
Louie Landale is the expert on the disappearing linkets problem. I hope I am not treading on his toes by posting the following:
This problem is sometimes caused by moving, deleting, renaming, or changing the Access rights (specifically remove “R” access) of one of the modules in a link set pairing. Link Set Pairings (LSPs) are stored using full name of the 3 modules (not the absolute ids), so changing the name or the path “corrupts” the LSP and the interface doesn't display it, although it is still there. linkset_delete.dxl (attached) can help fix some instances of disappearing link sets. It can find and restore or remove these invisible corrupted LSPs (Called Link Module Descriptors (LMDs) in DXL). Alternatively, if you restore the module with the same name in the same location, the LSPs will reappear
-
Open the folder that contains the module with the corrupted LSPs.
-
Load and run the DXL.
-
A window will open that displays all the linksets it has found. Select the ones you want to delete (if any). If none, just close the window.
-
The DXL output displayed at the bottom of the window should list all the LSPs it has found, including the corrupted ones. If the missing ones are listed, they can probably be restored.
-
Close the DXL window.
-
Open the module with the corrupted LSPs
-
Module Properties->Linksets.
-
With luck the corrupted LSPs should now have been restored and the problem is fixed.
-
If the LSPs are not restored, try restoring the module (as mentioned above).
-
If that fails, the last resort is re-adding each of the LSPs manually.
Hope this helps.
Ken.
Joined Telelogic DOORS forum 12-Sep-2003.
DOORS 8.2, running on Windows 2000 Server, accessed via Citrix.
Attachments
attachment_14294594_linkset_delete.dxl
|
|
Re: Linkset not appearing in the Module llandale - Fri Sep 11 11:27:04 EDT 2009
An actual 'LinkSet' is an object in a Link Module and is characterized by a unique Source formal module and unique Target formal module. You cannot have two 'LinkSets' in a Link Module with the same Source and Target. Actual 'Links' must be associated with a LinkSet, said to be 'in XYZ LinkSet' or 'in XYZ Link Module'.
A 'LinkSet Pairing' is a piece of information that is used for a module when a link is created; intended to direct that link to be in a particular 'LinkSet'.
Analogy: At the Car Rental, a 'Car' is a 'LinkSet' and the 'DisplayBoard' that tells you the location of your car is a 'LinkSet Pairing'.
Its confusing, but the Module >>Properties 'LinkSet' tab is not talking about 'LinkSets', its talking about 'LinkSet Pairings'. There you can control in which Link Module future links are created. The 'LinkSet' doesn't need to exist in order to define a 'LinkSet Pairing', but the Link Module and Target Module must exist.
Its more confusing, because in DXL a 'LinkSet Pairing' LSP is known as 'Link Module Descriptor' LMD.
Its even more confusing because the LMDs ..err.. the LSPs of modules are actually stored in that module's Folder, not in the module. That doesn't matter to the GUI but it does to DXL, you loop through the LMDs in a particular folder, then read the source and target module names.
Its exasperating because unlike just about every other reference to modules in DOORS (which use the module's UniqueID), LSPs ..err.. LMDs store the source and target module NAMEs. This means:
Those with Write access to the folder but not to the module can still use DXL to manipulate LMDs.
If you move the target or source module the LSP is no good and invisible in the GUI.
<c> You can defeat strict LSP directions and get your links in a different link module by simply renaming the target, create the links in whatever Link Module you like, then rename it back.
You are not the first to get confused.
|
|
Re: Linkset not appearing in the Module llandale - Fri Sep 11 11:31:00 EDT 2009 llandale - Fri Sep 11 11:27:04 EDT 2009
An actual 'LinkSet' is an object in a Link Module and is characterized by a unique Source formal module and unique Target formal module. You cannot have two 'LinkSets' in a Link Module with the same Source and Target. Actual 'Links' must be associated with a LinkSet, said to be 'in XYZ LinkSet' or 'in XYZ Link Module'.
A 'LinkSet Pairing' is a piece of information that is used for a module when a link is created; intended to direct that link to be in a particular 'LinkSet'.
Analogy: At the Car Rental, a 'Car' is a 'LinkSet' and the 'DisplayBoard' that tells you the location of your car is a 'LinkSet Pairing'.
Its confusing, but the Module >>Properties 'LinkSet' tab is not talking about 'LinkSets', its talking about 'LinkSet Pairings'. There you can control in which Link Module future links are created. The 'LinkSet' doesn't need to exist in order to define a 'LinkSet Pairing', but the Link Module and Target Module must exist.
Its more confusing, because in DXL a 'LinkSet Pairing' LSP is known as 'Link Module Descriptor' LMD.
Its even more confusing because the LMDs ..err.. the LSPs of modules are actually stored in that module's Folder, not in the module. That doesn't matter to the GUI but it does to DXL, you loop through the LMDs in a particular folder, then read the source and target module names.
Its exasperating because unlike just about every other reference to modules in DOORS (which use the module's UniqueID), LSPs ..err.. LMDs store the source and target module NAMEs. This means:
Those with Write access to the folder but not to the module can still use DXL to manipulate LMDs.
If you move the target or source module the LSP is no good and invisible in the GUI.
<c> You can defeat strict LSP directions and get your links in a different link module by simply renaming the target, create the links in whatever Link Module you like, then rename it back.
You are not the first to get confused.
.. and I'm not the first to use special characters and forget to 'Preview' my posts; although I may be the one that's failed that the most often.
|
|
Re: Linkset not appearing in the Module moonray - Fri Sep 11 12:17:18 EDT 2009 llandale - Fri Sep 11 11:27:04 EDT 2009
An actual 'LinkSet' is an object in a Link Module and is characterized by a unique Source formal module and unique Target formal module. You cannot have two 'LinkSets' in a Link Module with the same Source and Target. Actual 'Links' must be associated with a LinkSet, said to be 'in XYZ LinkSet' or 'in XYZ Link Module'.
A 'LinkSet Pairing' is a piece of information that is used for a module when a link is created; intended to direct that link to be in a particular 'LinkSet'.
Analogy: At the Car Rental, a 'Car' is a 'LinkSet' and the 'DisplayBoard' that tells you the location of your car is a 'LinkSet Pairing'.
Its confusing, but the Module >>Properties 'LinkSet' tab is not talking about 'LinkSets', its talking about 'LinkSet Pairings'. There you can control in which Link Module future links are created. The 'LinkSet' doesn't need to exist in order to define a 'LinkSet Pairing', but the Link Module and Target Module must exist.
Its more confusing, because in DXL a 'LinkSet Pairing' LSP is known as 'Link Module Descriptor' LMD.
Its even more confusing because the LMDs ..err.. the LSPs of modules are actually stored in that module's Folder, not in the module. That doesn't matter to the GUI but it does to DXL, you loop through the LMDs in a particular folder, then read the source and target module names.
Its exasperating because unlike just about every other reference to modules in DOORS (which use the module's UniqueID), LSPs ..err.. LMDs store the source and target module NAMEs. This means:
Those with Write access to the folder but not to the module can still use DXL to manipulate LMDs.
If you move the target or source module the LSP is no good and invisible in the GUI.
<c> You can defeat strict LSP directions and get your links in a different link module by simply renaming the target, create the links in whatever Link Module you like, then rename it back.
You are not the first to get confused.
Louie,
That was a great exposition about linkset pairings.
Thanks for taking the time to share it with us.
|
|